Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

changesets for branch dev #5554

Merged
merged 1 commit into from
Sep 27, 2024
Merged

changesets for branch dev #5554

merged 1 commit into from
Sep 27, 2024

Conversation

neo4j-team-graphql
Copy link
Collaborator

@neo4j-team-graphql neo4j-team-graphql commented Sep 11, 2024

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to dev, this PR will be updated.

Releases

@neo4j/[email protected]

Minor Changes

Patch Changes

  • #5583 d35b00d Thanks @angrykoala! - Deprecates top level arguments for nested operations on updates in favor of traversing the update argument. The deprecated arguments are:

    • create
    • delete
    • connect
    • disconnect
    • connectOrCreate

    For example, for create:

    deprecated

    mutation UpdatePeople {
        updatePeople(create: { movies: { node: { title: "The Good" } } }) {
            people {
                name
            }
        }
    }

    recommended

    mutation UpdatePeople {
        updatePeople(update: { movies: { create: { node: { title: "The Good" } } } }) {
            people {
                name
            }
        }
    }

    These deprecated arguments can be removed from the schema with the flag nestedUpdateOperationsFields in excludeDeprecatedFields:

    const neoSchema = new Neo4jGraphQL({
        typeDefs,
        features: {
            excludeDeprecatedFields: {
                nestedUpdateOperationsFields: true,
            },
        },
    });
  • #5585 21c18ee Thanks @mjfwebb! - Fix: standard JWT claim fields can now correctly be used even when a custom JWT payload is not defined.

  • #5590 e95db9c Thanks @angrykoala! - Fix subscriptions with autogenerated uids Subscriptions using id_IN operator parse uuids as integers #5586

@neo4j/[email protected]

Patch Changes

@neo4j-team-graphql neo4j-team-graphql force-pushed the changeset-release/dev branch 20 times, most recently from bd03b0d to 8f1b8dc Compare September 18, 2024 22:52
@neo4j-team-graphql neo4j-team-graphql force-pushed the changeset-release/dev branch 10 times, most recently from a813428 to 2f6579d Compare September 24, 2024 21:39
@neo4j-team-graphql neo4j-team-graphql force-pushed the changeset-release/dev branch 3 times, most recently from b227a6c to 63b4dc5 Compare September 26, 2024 15:36
@angrykoala angrykoala merged commit c3630fd into dev Sep 27, 2024
87 of 91 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants